Thanks you for creating the PR! The difference between creating streams and consumers is server side - for consumers, there used to be a single API for both creating and updating a consumer, thus it was a single operation on the client (that will change with the upcoming server release though, and we will be adding CreateConsumer and UpdateConsumer to the client as well). For streams, there are 2 separate APIs which means we can do safe creates and safe updates, which should usually be the preferred way.

That said, I am not strongly against adding CreateOrUpdateStream as convenience method, however that should probably be then reflected in other client libraries as well. Let me get back to you with this.

Thanks you for creating the PR! The difference between creating streams and consumers is server side - for consumers, there used to be a single API for both creating and updating a consumer, thus it was a single operation on the client (that will change with the upcoming server release though, and we will be adding CreateConsumer and UpdateConsumer to the client as well). For streams, there are 2 separate APIs which means we can do safe creates and safe updates, which should usually be the preferred way.

That said, I am not strongly against adding CreateOrUpdateStream as convenience method, however that should probably be then reflected in other client libraries as well. Let me get back to you with this.

Thanks :) I would be happy to help to implement this function in other clients

this feature is going to be a very very useful feature and will use it definitely.

Cool feature. Bravo @samanebi

All requested changes has been applied
@piotrpio

I am wondering when do you plan on merging this PR ?
@piotrpio

I am wondering when do you plan on merging this PR ? @piotrpio

Is there any update on this? I have done the suggested changes and also re requested review to @piotrpio
@piotrpio
@Jarema
@derekcollison

@samanebi Sorry for the delay, looks good! It'll be a part of the next release.